.NET: Fix AzureFunctions integration tests - set FUNCTIONS_WORKER_RUNTIME#6425
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Fixes CI failures in the .NET Azure Functions integration tests by ensuring Azure Functions Core Tools v4 can correctly determine the worker runtime when local.settings.json is not present (as in CI). This re-enables the previously skipped sample validation test suites.
Changes:
- Set
FUNCTIONS_WORKER_RUNTIME=dotnet-isolatedin bothStartFunctionApphelpers used by the integration tests. - Remove temporary
[Fact(... Skip=...)]/[RetryFact(... Skip=...)]attributes so the affected tests run again.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| dotnet/tests/Microsoft.Agents.AI.Hosting.AzureFunctions.IntegrationTests/WorkflowSamplesValidation.cs | Re-enables workflow sample tests and sets FUNCTIONS_WORKER_RUNTIME when launching the workflow Azure Functions samples. |
| dotnet/tests/Microsoft.Agents.AI.Hosting.AzureFunctions.IntegrationTests/SamplesValidation.cs | Re-enables durable agent sample tests and sets FUNCTIONS_WORKER_RUNTIME when launching the Azure Functions samples. |
SergeyMenshykh
approved these changes
Jun 10, 2026
westey-m
approved these changes
Jun 10, 2026
peibekwe
approved these changes
Jun 10, 2026
Azure Functions Core Tools v4 can no longer auto-detect the worker runtime when local.settings.json is absent. Add the required FUNCTIONS_WORKER_RUNTIME=dotnet-isolated environment variable to both StartFunctionApp helpers and re-enable the skipped tests. Fixes: #6402 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
peibekwe
approved these changes
Jun 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation and Context
Azure Functions Core Tools v4 can no longer auto-detect the
dotnet-isolatedworker runtime whenlocal.settings.jsonis absent (it's gitignored). This caused all 12SamplesValidationandWorkflowSamplesValidationintegration tests to fail in CI with:Fixes: #6402
Description
FUNCTIONS_WORKER_RUNTIME=dotnet-isolatedenvironment variable to bothStartFunctionApphelpers inSamplesValidation.csandWorkflowSamplesValidation.csContribution Checklist